update: details on Navigation 3 implementation available in CMP 1.10 #591
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
terrakok
requested changes
Dec 16, 2025
|
|
||
| ```text | ||
| [versions] | ||
| compose-multiplatform-navigation3 = "1.0.0-alpha05" |
Member
There was a problem hiding this comment.
I would name it just multiplatform-nav3 and multiplatform-nav3-ui
|
|
||
| > While Navigation 3 is released as two artifacts, `navigation3:navigation3-ui` and `navigation3:navigation3-common`, | ||
| > only `navigation-ui` needs a separate Compose Multiplatform implementation. | ||
| > A dependency on `navigation3-common` is added implicitly. |
| ``` | ||
|
|
||
| Finally, you can try out the [proof-of-concept library](https://github.com/terrakok/navigation3-browser) | ||
| authored by a JetBrains engineer that adds support for Navigation 3 to web targets: |
Member
There was a problem hiding this comment.
the library already supports web targets. my library adds an integration with browser history buttons
terrakok
approved these changes
Dec 18, 2025
ElviraMustafina
requested changes
Dec 19, 2025
Collaborator
ElviraMustafina
left a comment
ElviraMustafina
left a comment
There was a problem hiding this comment.
Sorry about the comment overload, got a bit too enthusiastic
| [//]: # (title: Navigation 3 in Compose Multiplatform) | ||
| <primary-label ref="alpha"/> | ||
|
|
||
| [Android's Navigation library](https://developer.android.com/guide/navigation) is upgraded to Navigation 3, a redesigned approach to navigation that works with |
Collaborator
There was a problem hiding this comment.
Suggested change
| [Android's Navigation library](https://developer.android.com/guide/navigation) is upgraded to Navigation 3, a redesigned approach to navigation that works with | |
| [Android's Navigation library](https://developer.android.com/guide/navigation) has been upgraded to Navigation 3, introducing a redesigned approach to navigation that works with |
|
|
||
| [Android's Navigation library](https://developer.android.com/guide/navigation) is upgraded to Navigation 3, a redesigned approach to navigation that works with | ||
| Compose and takes into account feedback to the previous version of the library. | ||
| Starting with the version 1.10, Compose Multiplatform helps adopt Navigation 3 into multiplatform projects on all supported platforms: |
Collaborator
There was a problem hiding this comment.
Suggested change
| Starting with the version 1.10, Compose Multiplatform helps adopt Navigation 3 into multiplatform projects on all supported platforms: | |
| Starting with version 1.10, Compose Multiplatform simplifies adopting Navigation 3 in multiplatform projects for all supported platforms: |
| ## General overview | ||
|
|
||
| Navigation 3 is more than a new version of the library — in a lot of ways it's a new library entirely. | ||
| To dive deeper into the philosophy behind it, see the [Android Developers blog post](https://android-developers.googleblog.com/2025/05/announcing-jetpack-navigation-3-for-compose.html). |
Collaborator
There was a problem hiding this comment.
Suggested change
| To dive deeper into the philosophy behind it, see the [Android Developers blog post](https://android-developers.googleblog.com/2025/05/announcing-jetpack-navigation-3-for-compose.html). | |
| To learn more about the philosophy behind this redesign, see the [Android Developers blog post](https://android-developers.googleblog.com/2025/05/announcing-jetpack-navigation-3-for-compose.html). |
| Navigation 3 is more than a new version of the library — in a lot of ways it's a new library entirely. | ||
| To dive deeper into the philosophy behind it, see the [Android Developers blog post](https://android-developers.googleblog.com/2025/05/announcing-jetpack-navigation-3-for-compose.html). | ||
|
|
||
| The major changes in the new library are: |
Collaborator
There was a problem hiding this comment.
Suggested change
| The major changes in the new library are: | |
| Key changes in Navigation 3 include: |
| The major changes in the new library are: | ||
|
|
||
| * **User-owned back stack**. Instead of operating a single library back stack, | ||
| you create and manage a `SnapshotStateList` of states which is observed by the UI. |
Collaborator
There was a problem hiding this comment.
I'm not sure about this one (feels like "Big UI is Watching You")
Suggested change
| you create and manage a `SnapshotStateList` of states which is observed by the UI. | |
| you create and manage a `SnapshotStateList` of states, which the UI observes directly. |
Comment on lines
+69
to
+70
| Navigation 3 is closely aligned with Compose and therefore a navigation implementation written for Android works in common | ||
| Compose Multiplatform code almost without changes. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Navigation 3 is closely aligned with Compose and therefore a navigation implementation written for Android works in common | |
| Compose Multiplatform code almost without changes. | |
| Navigation 3 is closely aligned with Compose, allowing an Android navigation implementation to work in common | |
| Compose Multiplatform code with minimal changes. |
|
|
||
| Navigation 3 is closely aligned with Compose and therefore a navigation implementation written for Android works in common | ||
| Compose Multiplatform code almost without changes. | ||
| The only thing you need to add to support non-JVM platforms like web and iOS is implement |
Collaborator
There was a problem hiding this comment.
Suggested change
| The only thing you need to add to support non-JVM platforms like web and iOS is implement | |
| To support non-JVM platforms like web and iOS, the only thing you need is to implement |
| To take this into account, the library has two overloads for the `rememberNavBackStack()` function: | ||
|
|
||
| * [The first overload](https://developer.android.com/reference/kotlin/androidx/navigation3/runtime/package-summary#rememberNavBackStack(kotlin.Array)) | ||
| only takes a set of `NavKey` and requires a reflection-based serializer. |
Collaborator
There was a problem hiding this comment.
set of NavKey elements? values?
| also takes a `SavedStateConfiguration` parameter that allows you to provide a `SerializersModule` and handle open polymorphism | ||
| correctly across all platforms. | ||
|
|
||
| In the multiplatform examples of Navigation 3 it can look [like this](https://github.com/terrakok/nav3-recipes/blob/8ff455499877225b638d5fcd82b232834f819422/sharedUI/src/commonMain/kotlin/com/example/nav3recipes/basicdsl/BasicDslActivity.kt#L40): |
Collaborator
There was a problem hiding this comment.
Suggested change
| In the multiplatform examples of Navigation 3 it can look [like this](https://github.com/terrakok/nav3-recipes/blob/8ff455499877225b638d5fcd82b232834f819422/sharedUI/src/commonMain/kotlin/com/example/nav3recipes/basicdsl/BasicDslActivity.kt#L40): | |
| In the Navigation 3 multiplatform examples, polymorphic serialization can look [like this](https://github.com/terrakok/nav3-recipes/blob/8ff455499877225b638d5fcd82b232834f819422/sharedUI/src/commonMain/kotlin/com/example/nav3recipes/basicdsl/BasicDslActivity.kt#L40): |
Comment on lines
+123
to
+124
| Sometimes this documentation uses Android-only examples, | ||
| but fundamental guidance and navigation principles are the same for Multiplatform: |
Collaborator
There was a problem hiding this comment.
Suggested change
| Sometimes this documentation uses Android-only examples, | |
| but fundamental guidance and navigation principles are the same for Multiplatform: | |
| While some of the documentation uses Android-specific examples, | |
| the core concepts and navigation principles remain consistent across all platforms: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.